Things we've learned implementing HubSpot for real companies. Written by the people doing the work, not the marketing team. No clickbait, no listicles.
The pattern repeats: kick-off feels great, the first sprint ships, then something goes quiet around week six. It's almost always the same root cause — and it isn't the software. Here's what we see, what we ask, and how to keep the second-month rot out of your own project.
Read the piece →The pattern repeats. The cause is almost never the software.
Most clients pay for ~30% more seats than they actively use. Here's how to find them.
Stop modelling what management wants to see. Model what reps already do.
What you can do with native HubSpot, what you need integrations for, where to draw the line.
The hardest part of an implementation isn't the implementation. Here's our post-launch playbook.
An opinionated stack for ops teams under 200 seats. With reasons.
Three rules. Two examples. One bad pattern to never use.
Activity history, ownership chains, and the custom object you'll be tempted to leave behind.
What to look for, what the role actually is, and how to keep them for longer than a year.
A two-page checklist we run the week before every release lands.
What to run, who to involve, and a template that's saved our clients about $400K to date.
Weighted, judgment, AI — what to use when, and what to ignore.